Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

chore(deps): update dependency aspect_rules_ts to v3 #1638

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

chore(deps): update dependency aspect_rules_ts to v3 #1638

wants to merge 2 commits into from

Conversation

renovate-bot
Copy link
Contributor

@renovate-bot renovate-bot commented Aug 15, 2024 •
edited
Loading

This PR contains the following updates:

Package Type Update Change
aspect_rules_ts http_archive major v1.4.5 -> v3.2.1

Release Notes

aspect-build/rules_ts (aspect_rules_ts)

v3.2.1

Compare Source

Using Bzlmod with Bazel 6:

Add to your MODULE.bazel file:

bazel_dep(name = "aspect_rules_ts", version = "3.2.1")

rules_ts_ext = use_extension("@​aspect_rules_ts//ts:extensions.bzl", "ext", dev_dependency = True)

rules_ts_ext.deps(
    ts_version_from = "//:package.json",
)

use_repo(rules_ts_ext, "npm_typescript")

Using WORKSPACE

Paste this snippet into your WORKSPACE file:

load("@​bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")
http_archive(
    name = "aspect_rules_ts",
    sha256 = "8bbac753f4b61adbfc1d9878b87b9cd0f64c9e8e6d8fafc8a1bbfa9625bab162",
    strip_prefix = "rules_ts-3.2.1",
    url = "https://github.com/aspect-build/rules_ts/releases/download/v3.2.1/rules_ts-v3.2.1.tar.gz",
)

##################

### rules_ts setup #
##################

### Fetches the rules_ts dependencies.
### If you want to have a different version of some dependency,

### you should fetch it *before* calling this.
### Alternatively, you can skip calling this function, so long as you've

### already fetched all the dependencies.
load("@​aspect_rules_ts//ts:repositories.bzl", "rules_ts_dependencies")

rules_ts_dependencies(

### This keeps the TypeScript version in-sync with the editor, which is typically best.
    ts_version_from = "//:package.json",

### Alternatively, you could pick a specific version, or use
### load("@​aspect_rules_ts//ts:repositories.bzl", "LATEST_TYPESCRIPT_VERSION")

### ts_version = LATEST_TYPESCRIPT_VERSION
)

load("@​aspect_rules_js//js:repositories.bzl", "rules_js_dependencies")

rules_js_dependencies()

load("@​aspect_rules_js//js:toolchains.bzl", "DEFAULT_NODE_VERSION", "rules_js_register_toolchains")

rules_js_register_toolchains(node_version = DEFAULT_NODE_VERSION)

### Register aspect_bazel_lib toolchains;
### If you use npm_translate_lock or npm_import from aspect_rules_js you can omit this block.
load("@​aspect_bazel_lib//lib:repositories.bzl", "register_copy_directory_toolchains", "register_copy_to_directory_toolchains")

register_copy_directory_toolchains()

register_copy_to_directory_toolchains()

To use rules_ts with bazel-lib 2.x, you must additionally register the coreutils toolchain.

load("@​aspect_bazel_lib//lib:repositories.bzl", "register_coreutils_toolchains")

register_coreutils_toolchains()

What's Changed

New Contributors

Full Changelog: aspect-build/rules_ts@v3.2.0...v3.2.1

v3.2.0

Compare Source

Using Bzlmod with Bazel 6:

Add to your MODULE.bazel file:

bazel_dep(name = "aspect_rules_ts", version = "3.2.0")

rules_ts_ext = use_extension("@​aspect_rules_ts//ts:extensions.bzl", "ext", dev_dependency = True)

rules_ts_ext.deps(
    ts_version_from = "//:package.json",
)

use_repo(rules_ts_ext, "npm_typescript")

Using WORKSPACE

Paste this snippet into your WORKSPACE file:

load("@​bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")
http_archive(
    name = "aspect_rules_ts",
    sha256 = "d23ba2b800493a83c3ec9e300e01c74a7b0a58c08893e681417e2c2f48f8c4bb",
    strip_prefix = "rules_ts-3.2.0",
    url = "https://github.com/aspect-build/rules_ts/releases/download/v3.2.0/rules_ts-v3.2.0.tar.gz",
)

##################

### rules_ts setup #
##################

### Fetches the rules_ts dependencies.
### If you want to have a different version of some dependency,

### you should fetch it *before* calling this.
### Alternatively, you can skip calling this function, so long as you've

### already fetched all the dependencies.
load("@​aspect_rules_ts//ts:repositories.bzl", "rules_ts_dependencies")

rules_ts_dependencies(

### This keeps the TypeScript version in-sync with the editor, which is typically best.
    ts_version_from = "//:package.json",

### Alternatively, you could pick a specific version, or use
### load("@​aspect_rules_ts//ts:repositories.bzl", "LATEST_TYPESCRIPT_VERSION")

### ts_version = LATEST_TYPESCRIPT_VERSION
)

load("@​aspect_rules_js//js:repositories.bzl", "rules_js_dependencies")

rules_js_dependencies()

load("@​aspect_rules_js//js:toolchains.bzl", "DEFAULT_NODE_VERSION", "rules_js_register_toolchains")

rules_js_register_toolchains(node_version = DEFAULT_NODE_VERSION)

### Register aspect_bazel_lib toolchains;
### If you use npm_translate_lock or npm_import from aspect_rules_js you can omit this block.
load("@​aspect_bazel_lib//lib:repositories.bzl", "register_copy_directory_toolchains", "register_copy_to_directory_toolchains")

register_copy_directory_toolchains()

register_copy_to_directory_toolchains()

To use rules_ts with bazel-lib 2.x, you must additionally register the coreutils toolchain.

load("@​aspect_bazel_lib//lib:repositories.bzl", "register_coreutils_toolchains")

register_coreutils_toolchains()

What's Changed

Full Changelog: aspect-build/rules_ts@v3.1.0...v3.2.0

v3.1.0

Compare Source

Using Bzlmod with Bazel 6:

Add to your MODULE.bazel file:

bazel_dep(name = "aspect_rules_ts", version = "3.1.0")

rules_ts_ext = use_extension("@​aspect_rules_ts//ts:extensions.bzl", "ext", dev_dependency = True)

rules_ts_ext.deps(
    ts_version_from = "//:package.json",
)

use_repo(rules_ts_ext, "npm_typescript")

Using WORKSPACE

Paste this snippet into your WORKSPACE file:

load("@​bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")
http_archive(
    name = "aspect_rules_ts",
    sha256 = "5aafa2422b6f2ed6d8db9edcd6368693055960bca7e149516b95c0d45a6a7ae5",
    strip_prefix = "rules_ts-3.1.0",
    url = "https://github.com/aspect-build/rules_ts/releases/download/v3.1.0/rules_ts-v3.1.0.tar.gz",
)

##################

### rules_ts setup #
##################

### Fetches the rules_ts dependencies.
### If you want to have a different version of some dependency,

### you should fetch it *before* calling this.
### Alternatively, you can skip calling this function, so long as you've

### already fetched all the dependencies.
load("@​aspect_rules_ts//ts:repositories.bzl", "rules_ts_dependencies")

rules_ts_dependencies(

### This keeps the TypeScript version in-sync with the editor, which is typically best.
    ts_version_from = "//:package.json",

### Alternatively, you could pick a specific version, or use
### load("@​aspect_rules_ts//ts:repositories.bzl", "LATEST_TYPESCRIPT_VERSION")

### ts_version = LATEST_TYPESCRIPT_VERSION
)

load("@​aspect_rules_js//js:repositories.bzl", "rules_js_dependencies")

rules_js_dependencies()

load("@​aspect_rules_js//js:toolchains.bzl", "DEFAULT_NODE_VERSION", "rules_js_register_toolchains")

rules_js_register_toolchains(node_version = DEFAULT_NODE_VERSION)

### Register aspect_bazel_lib toolchains;
### If you use npm_translate_lock or npm_import from aspect_rules_js you can omit this block.
load("@​aspect_bazel_lib//lib:repositories.bzl", "register_copy_directory_toolchains", "register_copy_to_directory_toolchains")

register_copy_directory_toolchains()

register_copy_to_directory_toolchains()

To use rules_ts with bazel-lib 2.x, you must additionally register the coreutils toolchain.

load("@​aspect_bazel_lib//lib:repositories.bzl", "register_coreutils_toolchains")

register_coreutils_toolchains()

What's Changed

Full Changelog: aspect-build/rules_ts@v3.0.0...v3.1.0

v3.0.0

Compare Source

Using Bzlmod with Bazel 6:

Add to your MODULE.bazel file:

bazel_dep(name = "aspect_rules_ts", version = "3.0.0")

rules_ts_ext = use_extension("@​aspect_rules_ts//ts:extensions.bzl", "ext", dev_dependency = True)

rules_ts_ext.deps(
    ts_version_from = "//:package.json",
)

use_repo(rules_ts_ext, "npm_typescript")

Using WORKSPACE

Paste this snippet into your WORKSPACE file:

load("@​bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")
http_archive(
    name = "aspect_rules_ts",
    sha256 = "ee7dcc35faef98f3050df9cf26f2a72ef356cab8ad927efb1c4dc119ac082a19",
    strip_prefix = "rules_ts-3.0.0",
    url = "https://github.com/aspect-build/rules_ts/releases/download/v3.0.0/rules_ts-v3.0.0.tar.gz",
)

##################

### rules_ts setup #
##################

### Fetches the rules_ts dependencies.
### If you want to have a different version of some dependency,

### you should fetch it *before* calling this.
### Alternatively, you can skip calling this function, so long as you've

### already fetched all the dependencies.
load("@​aspect_rules_ts//ts:repositories.bzl", "rules_ts_dependencies")

rules_ts_dependencies(

### This keeps the TypeScript version in-sync with the editor, which is typically best.
    ts_version_from = "//:package.json",

### Alternatively, you could pick a specific version, or use
### load("@​aspect_rules_ts//ts:repositories.bzl", "LATEST_TYPESCRIPT_VERSION")

### ts_version = LATEST_TYPESCRIPT_VERSION
)

load("@​aspect_rules_js//js:repositories.bzl", "rules_js_dependencies")

rules_js_dependencies()

load("@​aspect_rules_js//js:toolchains.bzl", "DEFAULT_NODE_VERSION", "rules_js_register_toolchains")

rules_js_register_toolchains(node_version = DEFAULT_NODE_VERSION)

### Register aspect_bazel_lib toolchains;
### If you use npm_translate_lock or npm_import from aspect_rules_js you can omit this block.
load("@​aspect_bazel_lib//lib:repositories.bzl", "register_copy_directory_toolchains", "register_copy_to_directory_toolchains")

register_copy_directory_toolchains()

register_copy_to_directory_toolchains()

To use rules_ts with bazel-lib 2.x, you must additionally register the coreutils toolchain.

load("@​aspect_bazel_lib//lib:repositories.bzl", "register_coreutils_toolchains")

register_coreutils_toolchains()

What's Changed

New Contributors

Full Changelog: aspect-build/rules_ts@v2.4.1...v3.0.0

v2.4.2

Compare Source

Using Bzlmod with Bazel 6:

Add to your MODULE.bazel file:

bazel_dep(name = "aspect_rules_ts", version = "2.4.2")

rules_ts_ext = use_extension("@​aspect_rules_ts//ts:extensions.bzl", "ext", dev_dependency = True)

rules_ts_ext.deps()

use_repo(rules_ts_ext, "npm_typescript")

Using WORKSPACE

Paste this snippet into your WORKSPACE file:

load("@​bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")
http_archive(
    name = "aspect_rules_ts",
    sha256 = "f69a6452b129d39d9b05f3dff8b1057185bb195b4daf0cff419988de757c6c31",
    strip_prefix = "rules_ts-2.4.2",
    url = "https://github.com/aspect-build/rules_ts/releases/download/v2.4.2/rules_ts-v2.4.2.tar.gz",
)

##################

### rules_ts setup #
##################

### Fetches the rules_ts dependencies.
### If you want to have a different version of some dependency,

### you should fetch it *before* calling this.
### Alternatively, you can skip calling this function, so long as you've

### already fetched all the dependencies.
load("@​aspect_rules_ts//ts:repositories.bzl", "rules_ts_dependencies")

rules_ts_dependencies(

### This keeps the TypeScript version in-sync with the editor, which is typically best.
    ts_version_from = "//:package.json",

### Alternatively, you could pick a specific version, or use
### load("@​aspect_rules_ts//ts:repositories.bzl", "LATEST_TYPESCRIPT_VERSION")

### ts_version = LATEST_TYPESCRIPT_VERSION
)

load("@​aspect_rules_js//js:repositories.bzl", "rules_js_dependencies")

rules_js_dependencies()

load("@​bazel_features//:deps.bzl", "bazel_features_deps")

bazel_features_deps()

### Fetch and register node, if you haven't already
load("@​rules_nodejs//nodejs:repositories.bzl", "DEFAULT_NODE_VERSION", "nodejs_register_toolchains")

nodejs_register_toolchains(
    name = "nodejs",
    node_version = DEFAULT_NODE_VERSION,
)

### Register aspect_bazel_lib toolchains;
### If you use npm_translate_lock or npm_import from aspect_rules_js you can omit this block.
load("@​aspect_bazel_lib//lib:repositories.bzl", "register_copy_directory_toolchains", "register_copy_to_directory_toolchains")

register_copy_directory_toolchains()

register_copy_to_directory_toolchains()

To use rules_ts with bazel-lib 2.x, you must additionally register the coreutils toolchain.

load("@​aspect_bazel_lib//lib:repositories.bzl", "register_coreutils_toolchains")

register_coreutils_toolchains()

Full Changelog: aspect-build/rules_ts@v2.4.1...v2.4.2

v2.4.1

Compare Source

Using Bzlmod with Bazel 6:

Add to your MODULE.bazel file:

bazel_dep(name = "aspect_rules_ts", version = "2.4.1")

rules_ts_ext = use_extension("@​aspect_rules_ts//ts:extensions.bzl", "ext", dev_dependency = True)

rules_ts_ext.deps()

use_repo(rules_ts_ext, "npm_typescript")

Using WORKSPACE

Paste this snippet into your WORKSPACE file:

load("@​bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")
http_archive(
    name = "aspect_rules_ts",
    sha256 = "da6620683ab2c28014e9c82e8a8fdbb724cd67f6a1d27317f42a8ceb14048b9b",
    strip_prefix = "rules_ts-2.4.1",
    url = "https://github.com/aspect-build/rules_ts/releases/download/v2.4.1/rules_ts-v2.4.1.tar.gz",
)

##################

### rules_ts setup #
##################

### Fetches the rules_ts dependencies.
### If you want to have a different version of some dependency,

### you should fetch it *before* calling this.
### Alternatively, you can skip calling this function, so long as you've

### already fetched all the dependencies.
load("@​aspect_rules_ts//ts:repositories.bzl", "rules_ts_dependencies")

rules_ts_dependencies(

### This keeps the TypeScript version in-sync with the editor, which is typically best.
    ts_version_from = "//:package.json",

### Alternatively, you could pick a specific version, or use
### load("@​aspect_rules_ts//ts:repositories.bzl", "LATEST_TYPESCRIPT_VERSION")

### ts_version = LATEST_TYPESCRIPT_VERSION
)

load("@​aspect_rules_js//js:repositories.bzl", "rules_js_dependencies")

rules_js_dependencies()

load("@​bazel_features//:deps.bzl", "bazel_features_deps")

bazel_features_deps()

### Fetch and register node, if you haven't already
load("@​rules_nodejs//nodejs:repositories.bzl", "DEFAULT_NODE_VERSION", "nodejs_register_toolchains")

nodejs_register_toolchains(
    name = "nodejs",
    node_version = DEFAULT_NODE_VERSION,
)

### Register aspect_bazel_lib toolchains;
### If you use npm_translate_lock or npm_import from aspect_rules_js you can omit this block.
load("@​aspect_bazel_lib//lib:repositories.bzl", "register_copy_directory_toolchains", "register_copy_to_directory_toolchains")

register_copy_directory_toolchains()

register_copy_to_directory_toolchains()

To use rules_ts with bazel-lib 2.x, you must additionally register the coreutils toolchain.

load("@​aspect_bazel_lib//lib:repositories.bzl", "register_coreutils_toolchains")

register_coreutils_toolchains()

What's Changed

Full Changelog: aspect-build/rules_ts@v2.4.0...v2.4.1

v2.4.0

Compare Source

Using Bzlmod with Bazel 6:

Add to your MODULE.bazel file:

bazel_dep(name = "aspect_rules_ts", version = "2.4.0")

rules_ts_ext = use_extension("@​aspect_rules_ts//ts:extensions.bzl", "ext", dev_dependency = True)

rules_ts_ext.deps()

use_repo(rules_ts_ext, "npm_typescript")

Using WORKSPACE

Paste this snippet into your WORKSPACE file:

load("@​bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")
http_archive(
    name = "aspect_rules_ts",
    sha256 = "97a8246bf6d1c7077b296e90a6e307bf8eabed02c5bca84d46db81efbf6ead41",
    strip_prefix = "rules_ts-2.4.0",
    url = "https://github.com/aspect-build/rules_ts/releases/download/v2.4.0/rules_ts-v2.4.0.tar.gz",
)

##################

### rules_ts setup #
##################

### Fetches the rules_ts dependencies.
### If you want to have a different version of some dependency,

### you should fetch it *before* calling this.
### Alternatively, you can skip calling this function, so long as you've

### already fetched all the dependencies.
load("@​aspect_rules_ts//ts:repositories.bzl", "rules_ts_dependencies")

rules_ts_dependencies(

### This keeps the TypeScript version in-sync with the editor, which is typically best.
    ts_version_from = "//:package.json",

### Alternatively, you could pick a specific version, or use
### load("@​aspect_rules_ts//ts:repositories.bzl", "LATEST_TYPESCRIPT_VERSION")

### ts_version = LATEST_TYPESCRIPT_VERSION
)

load("@​aspect_rules_js//js:repositories.bzl", "rules_js_dependencies")

rules_js_dependencies()

load("@​bazel_features//:deps.bzl", "bazel_features_deps")

bazel_features_deps()

### Fetch and register node, if you haven't already
load("@​rules_nodejs//nodejs:repositories.bzl", "DEFAULT_NODE_VERSION", "nodejs_register_toolchains")

nodejs_register_toolchains(
    name = "nodejs",
    node_version = DEFAULT_NODE_VERSION,
)

### Register aspect_bazel_lib toolchains;
### If you use npm_translate_lock or npm_import from aspect_rules_js you can omit this block.
load("@​aspect_bazel_lib//lib:repositories.bzl", "register_copy_directory_toolchains", "register_copy_to_directory_toolchains")

register_copy_directory_toolchains()

register_copy_to_directory_toolchains()

To use rules_ts with bazel-lib 2.x, you must additionally register the coreutils toolchain.

load("@​aspect_bazel_lib//lib:repositories.bzl", "register_coreutils_toolchains")

register_coreutils_toolchains()

What's Changed

Full Changelog: aspect-build/rules_ts@v2.3.0...v2.4.0

v2.3.0

Compare Source

Using Bzlmod with Bazel 6:

Add to your MODULE.bazel file:

bazel_dep(name = "aspect_rules_ts", version = "2.3.0")

rules_ts_ext = use_extension("@​aspect_rules_ts//ts:extensions.bzl", "ext", dev_dependency = True)

rules_ts_ext.deps()

use_repo(rules_ts_ext, "npm_typescript")

Using WORKSPACE

Paste this snippet into your WORKSPACE file:

load("@​bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")
http_archive(
    name = "aspect_rules_ts",
    sha256 = "b11f5bd59983a58826842029b99240fd0eeb6f1291d710db10f744b327701646",
    strip_prefix = "rules_ts-2.3.0",
    url = "https://github.com/aspect-build/rules_ts/releases/download/v2.3.0/rules_ts-v2.3.0.tar.gz",
)

##################

### rules_ts setup #
##################

### Fetches the rules_ts dependencies.
### If you want to have a different version of some dependency,

### you should fetch it *before* calling this.
### Alternatively, you can skip calling this function, so long as you've

### already fetched all the dependencies.
load("@​aspect_rules_ts//ts:repositories.bzl", "rules_ts_dependencies")

rules_ts_dependencies(

### This keeps the TypeScript version in-sync with the editor, which is typically best.
    ts_version_from = "//:package.json",

### Alternatively, you could pick a specific version, or use
### load("@​aspect_rules_ts//ts:repositories.bzl", "LATEST_TYPESCRIPT_VERSION")

### ts_version = LATEST_TYPESCRIPT_VERSION
)

load("@​aspect_rules_js//js:repositories.bzl", "rules_js_dependencies")

rules_js_dependencies()

load("@​bazel_features//:deps.bzl", "bazel_features_deps")

bazel_features_deps()

### Fetch and register node, if you haven't already
load("@​rules_nodejs//nodejs:repositories.bzl", "DEFAULT_NODE_VERSION", "nodejs_register_toolchains")

nodejs_register_toolchains(
    name = "nodejs",
    node_version = DEFAULT_NODE_VERSION,
)

### Register aspect_bazel_lib toolchains;
### If you use npm_translate_lock or npm_import from aspect_rules_js you can omit this block.
load("@​aspect_bazel_lib//lib:repositories.bzl", "register_copy_directory_toolchains", "register_copy_to_directory_toolchains")

register_copy_directory_toolchains()

register_copy_to_directory_toolchains()

To use rules_ts with bazel-lib 2.x, you must additionally register the coreutils toolchain.

load("@​aspect_bazel_lib//lib:repositories.bzl", "register_coreutils_toolchains")

register_coreutils_toolchains()

What's Changed

New Contributors

Full Changelog: aspect-build/rules_ts@v2.2.0...v2.3.0

v2.2.0

Compare Source

Using Bzlmod with Bazel 6:

Add to your MODULE.bazel file:

bazel_dep(name = "aspect_rules_ts", version = "2.2.0")

rules_ts_ext = use_extension(
    "@​aspect_rules_ts//ts:extensions.bzl",
    "ext",
    dev_dependency = True,
)

rules_ts_ext.deps()

use_repo(rules_ts_ext, "npm_typescript")

Using WORKSPACE

Paste this snippet into your WORKSPACE file:

load("@​bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")
http_archive(
    name = "aspect_rules_ts",
    sha256 = "c77f0dfa78c407893806491223c1264c289074feefbf706721743a3556fa7cea",
    strip_prefix = "rules_ts-2.2.0",
    url = "https://github.com/aspect-build/rules_ts/releases/download/v2.2.0/rules_ts-v2.2.0.tar.gz",
)

##################

### rules_ts setup #
##################

### Fetches the rules_ts dependencies.
### If you want to have a different version of some dependency,

### you should fetch it *before* calling this.
### Alternatively, you can skip calling this function, so long as you've

### already fetched all the dependencies.
load("@​aspect_rules_ts//ts:repositories.bzl", "rules_ts_dependencies")

rules_ts_dependencies(

### This keeps the TypeScript version in-sync with the editor, which is typically best.
    ts_version_from = "//:package.json",

### Alternatively, you could pick a specific version, or use
### load("@​aspect_rules_ts//ts:repositories.bzl", "LATEST_TYPESCRIPT_VERSION")

### ts_version = LATEST_TYPESCRIPT_VERSION
)

load("@​aspect_rules_js//js:repositories.bzl", "rules_js_dependencies")

rules_js_dependencies()

load("@​bazel_features//:deps.bzl", "bazel_features_deps")

bazel_features_deps()

### Fetch and register node, if you haven't already
load("@​rules_nodejs//nodejs:repositories.bzl", "DEFAULT_NODE_VERSION", "nodejs_register_toolchains")

nodejs_register_toolchains(
    name = "nodejs",
    node_version = DEFAULT_NODE_VERSION,
)

### Register aspect_bazel_lib toolchains;
### If you use npm_translate_lock or npm_import from aspect_rules_js you can omit this block.
load("@​aspect_bazel_lib//lib:repositories.bzl", "register_copy_directory_toolchains", "register_copy_to_directory_toolchains")

register_copy_directory_toolchains()

register_copy_to_directory_toolchains()

To use rules_ts with bazel-lib 2.x, you must additionally register the coreutils toolchain.

load("@​aspect_bazel_lib//lib:repositories.bzl", "register_coreutils_toolchains")

register_coreutils_toolchains()

What's Changed

New Contributors

Full Changelog: aspect-build/rules_ts@v2.1.1...v2.2.0

v2.1.1

Compare Source

Using Bzlmod with Bazel 6:

Add to your MODULE.bazel file:

bazel_dep(name = "aspect_rules_ts", version = "2.1.1")

rules_ts_ext = use_extension(
    "@​aspect_rules_ts//ts:extensions.bzl",
    "ext",
    dev_dependency = True,
)

rules_ts_ext.deps()

use_repo(rules_ts_ext, "npm_typescript")

Using WORKSPACE

Paste this snippet into your WORKSPACE file:

load("@​bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")
http_archive(
    name = "aspect_rules_ts",
    sha256 = "6ad28b5bac2bb5a74e737925fbc3f62ce1edabe5a48d61a9980c491ef4cedfb7",
    strip_prefix = "rules_ts-2.1.1",
    url = "https://github.com/aspect-build/rules_ts/releases/download/v2.1.1/rules_ts-v2.1.1.tar.gz",
)

##################

### rules_ts setup #
##################

### Fetches the rules_ts dependencies.
### If you want to have a different version of some dependency,

### you should fetch it *before* calling this.
### Alternatively, you can skip calling this function, so long as you've

### already fetched all the dependencies.
load("@​aspect_rules_ts//ts:repositories.bzl", "rules_ts_dependencies")

rules_ts_dependencies(

### This keeps the TypeScript version in-sync with the editor, which is typically best.
    ts_version_from = "//:package.json",

### Alternatively, you could pick a specific version, or use
### load("@​aspect_rules_ts//ts:repositories.bzl", "LATEST_TYPESCRIPT_VERSION")

### ts_version = LATEST_TYPESCRIPT_VERSION
)

load("@​aspect_rules_js//js:repositories.bzl", "rules_js_dependencies")

rules_js_dependencies()

load("@​bazel_features//:deps.bzl", "bazel_features_deps")

bazel_features_deps()

### Fetch and register node, if you haven't already
load("@​rules_nodejs//nodejs:repositories.bzl", "DEFAULT_NODE_VERSION", "nodejs_register_toolchains")

nodejs_register_toolchains(
    name = "nodejs",
    node_version = DEFAULT_NODE_VERSION,
)

### Register aspect_bazel_lib toolchains;
### If you use npm_translate_lock or npm_import from aspect_rules_js you can omit this block.
load("@​aspect_bazel_lib//lib:repositories.bzl", "register_copy_directory_toolchains", "register_copy_to_directory_toolchains")

register_copy_directory_toolchains()

register_copy_to_directory_toolchains()

To use rules_ts with bazel-lib 2.x, you must additionally register the coreutils toolchain.

load("@​aspect_bazel_lib//lib:repositories.bzl", "register_coreutils_toolchains")

register_coreutils_toolchains()

What's Changed

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate-bot renovate-bot requested review from a team as code owners August 15, 2024 06:45
@trusted-contributions-gcf trusted-contributions-gcf bot added the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Aug 15, 2024
@forking-renovate Forking Renovate
Copy link

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@sofisl sofisl sofisl approved these changes

Assignees
No one assigned
Labels
kokoro:force-run Add this label to force Kokoro to re-run the tests.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@renovate-bot @sofisl